Config pipeline #1005
Config pipeline #1005
Conversation
…integration test output to stdout
…junit_report and setup_goreleaser
bitrise.yml
Outdated
| - bundle::run_integration_tests: { } | ||
| meta: | ||
| bitrise.io: | ||
| stack: osx-xcode-16.0.x |
There was a problem hiding this comment.
How about running on osx-xcode-latest, which is a pointer to the latest edge stack? We do this in some build platform projects, it has two benefits:
- Dogfoods the edge stacks, which often have experimental fixes and changes applied
- This stack ID will never be removed or become invalid, there is no need to manually update it after a stack gets deprecated
| meta: | ||
| bitrise.io: | ||
| machine_type_id: elite-xl | ||
| stack: linux-docker-android-20.04 # TODO: Docker tests are failing on Ubuntu 22.04 |
There was a problem hiding this comment.
ACK, we have a ticket for this in the BE backlog
| - script: | ||
| title: Skipping success | ||
| is_always_run: false | ||
| go install github.com/jstemmer/go-junit-report/v2@latest |
There was a problem hiding this comment.
nit: would be good to pin the version
There was a problem hiding this comment.
Hmm, do we want to pin an exact version? Currently, we pin the major version 2 (github.com/jstemmer/go-junit-report/v2)
There was a problem hiding this comment.
Yeah, that could be enough, but I also don't see any reason not to pin an exact version. A commit hash won't disappear from GitHub (well, it could be force-pushed, but let's hope it never happens)
bitrise.yml
Outdated
| is_always_run: false | ||
| go install github.com/jstemmer/go-junit-report/v2@latest | ||
| if [ "$(uname)" == "Linux" ] && command -v asdf >/dev/null && asdf plugin list | grep -q 'golang'; then | ||
| asdf reshim golang |
There was a problem hiding this comment.
I usually just do asdf reshim golang || true, don't overthink it, this is Bash 😆
Checklist
README.mdis updated with the changes (if needed)Version
Requires a NO version update
Context
This PR merges the project's macOS and Linux CI workflows into a single Pipeline and switches to a repository stored bitrise.yml.
The new
cipripeline runs unit, integration and binary build tests in both Linux and macOS machines in parallel. The previous sequential CI workflows are converted into step bundles and executed in stacks specific workflows:checkworkflow ->run_lintandrun_unit_testsstep bundles, executed inrun_lint,run_unit_tests_macosandrun_unit_tests_linuxworkflowsintegration-testworkflow ->run_integration_testsandrun_docker_integration_testssteps bundles, executed inrun_integration_tests_macos,run_integration_tests_linuxandrun_docker_integration_tests_linuxworkflowstest-binary-buildworkflow ->test_binary_build_macosandtest_binary_build_linuxThe new config's trigger map and
releaseworkflow is coming from the Bitrise.io stored bitrise.yml.The new
run_unit_testsandrun_integration_testsstep bundles are exporting test results for the testing adding.